Selecting ggsn in shared mobile network

ABSTRACT

The invention relates to the packet switched portion of a mobile communications system in which two or more network operators share the same network. To allow the operators to compete with each other, they usually have a gateway node (GGSN 1 , GGSN 2 ) of their own, although they share the serving node (SGSN 1 ). In order to enable the selection of the gateway node (GGSN 1 , GGSN 2 ), the invention involves maintaining information about predefined partner networks, i.e. shared networks an operator has in addition to its own networks. On the basis of the information a mobile station (MS 2 ) can be connected to a gateway node (GGSN 2 ) of its home network (PLMN 2 ), provided that the visited network (PLMN 1 ) is a partner network of the home network (PLMN 2 ). A visiting mobile station from outside the partner networks, however, can be connected to the visited gateway node (GGSN 1 ).

BACKGROUND OF THE INVENTION

The invention relates to packet switched portions of mobile networks, and particularly to the sharing of a Serving GPRS Support Node (SGSN) in a radio network shared by different network operators. The General Packet Radio Service (GPRS) was designed to alleviate the drawbacks of the GSM system (the Global System for Mobile Communications) and to allow packet switched applications to be used in a mobile network. GPRS networks are also used for third generation mobile networks.

Third generation mobile operators are interested in applying a shared network in such a way that two or more operators would use a common radio network and a common SGSN as well. This would allow costs related to network construction and maintenance, for example, to be reduced and, in addition, a shared network may be used in various cases. For example, the two or more operators may decide to share the costs of the network. One possibility is that each one of the operators covers only a part of a country, or, in the case of two operators, a half of it. Another possibility is that the operators cover a certain area (e.g. a rural area) with a shared network belonging to all of them. This shared network is then an equivalent network to the home network of a Mobile Station (MS) belonging to one of the operators. The shared network will not have a subscriber register (HLR, Home Location Register) and may not have a Gateway GPRS Support Node (GGSN).Another example is an ‘established operator’ who has a national roaming agreement with a ‘greenfield operator’, so that in a part of the country (e.g. a rural area), the greenfield operator uses the established operator's coverage. The established operator's network is thus equivalent to the home network of an MS (belonging to the greenfield operator).

The operators of shared networks will be competing with each other by offering diverse subscriber connections and services, and therefore all the operators have preferably at least one GGSN of their own. A Mobile Virtual Network Operator (MVNO) may only have GGSNs and an HLR, and it gains access through other operators.

A problem in the above arrangement is that the SGSNs currently employ methods in which the GGSN of the network where a mobile station is located at a given moment is selected as its GGSN, which is thus not necessarily the GGSN of its home network. There is a method that can be used to alleviate the problem. It comprises using a flag in the HLR, i.e. a “VPLMN address allowed”-flag is set to ‘No’ to force the GGSN of the home network to always serve as the GGSN. The problem with this solution is that it directs the mobile station to use the GGSN of the home network also in those visiting networks that are not equivalent to the home network of the mobile station. For example, when roaming is concerned, it is not always desirable to use the home GGSN, because a closer GGSN (in the visited country) may offer the same services (i.e. APN, Access Point Name). Obviously, if the MS is located in its home country but served by an equivalent PLMN, the home GGSN is usually physically quite close.

BRIEF DESCRIPTION OF THE INVENTION

It is therefore an object of the invention to provide a method and an apparatus implementing the method to enable the above problem to be solved. This is achieved by a method, system and network nodes, which are characterized by what is stated in the independent claims. The preferred embodiments of the invention are disclosed in the dependent claims.

The underlying idea of the invention is that information relating to predefined partner networks that are equivalent to the home network is maintained in mobile networks, the information being checked when a mobile station is to be connected to a GGSN.

In this context, the term ‘home network’ is used to refer to the actual home network of a mobile station, i.e. to the network of its home network operator. The term ‘partner network’ refers to a network having an agreement to provide access to the other network and/or to gain access through the other network. Examples of partner network operators are MVNOs or roaming partners. The term ‘shared network’ refers to networks providing access to more than one operator. In other words ‘a shared network element’ can be a property of a first network but a second network may use it. It can also be commonly owned by the first and the second network. The term ‘equivalent network’ is used for networks that are equivalent to the home network.

An advantage of the method and system of the invention is that on the basis of the partner information maintained in the system, the appropriate GGSN can be selected on the basis of the home PLMN of the MS and on the network where the MS is located.

In particular, a GGSN located in a network belonging to the home operator can be selected when appropriate (i.e. a GGSN managed by the home operator is located in the same or a near-by country). For example, a mobile station located in a predefined partner network equivalent to its home network can be connected to the GGSN of the home network. When the mobile station is outside the home network and predefined partner networks of the home network, it can be connected to a visited GGSN.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, the invention will be described with reference to preferred embodiments and the accompanying drawings, in which

FIG. 1 illustrates the architecture of a shared mobile network;

FIGS. 2, 3 and 4 illustrate the selection of the GGSN.

DETAILED DESCRIPTION OF THE INVENTION

In the following, preferred embodiments of the invention will be described with reference to a third generation mobile communications system, such as the UMTS (Universal Mobile Communications System). This invention is not, however, meant to be restricted to these embodiments. Consequently, the invention may be applied in any mobile communications system that provides GPRS-type packet switched radio service capable of transmitting packet-switched data. Examples of other systems include the IMT-2000, IS-41, GSM, or the like, such as the PCS (Personal Communication System) or the DCS 1800 (Digital Cellular System for 1800 MHz). The specifications of mobile communications systems and particularly those of the IMT-2000 and the UMTS advance rapidly. This may require additional changes to the invention. For this reason, the terminology and the expressions used should be interpreted in their broadest sense since they meant to illustrate the invention and not to restrict it. The relevant inventive aspect is the functionality concerned, not the network element or equipment where it is executed.

FIG. 1 shows a simplified architecture of the packet switched portion of the UMTS in which only the elements essential for the invention are included. It is apparent to a person skilled in the art that a common mobile communications system also comprises other functions and structures that need not be described in greater detail in this context. The main components of the UMTS (Core Network CN1, Universal Terrestrial Radio Access Network UTRAN1) are well known and will not be described in detail herein. In the UMTS, the interface between the core network CN1 and the UTRAN1 is referred to as Iu and the air interface (radio interface) between the UTRAN1 and the mobile station MS is referred to as Uu. PLMN1 and PLMN2 refer to two separate mobile networks, which belong to different operators and may be predefined partner networks equivalent to each other.

UTRAN is a conceptual term for a third generation radio network, and it identifies a network part between the Iu- and Uu-interfaces, the network part comprising radio network controllers RNC and base stations BS (Node B).

A Radio Network Controller RNC is a network node that is responsible for controlling the radio resources of the UTRAN. Logically, it corresponds to a Base Station Controller (BSC) in the GSM. In FIG. 1 the RNC is connected to a node of the core network CN1, i.e. to an SGSN1.

The core network CN1 may be connected to external networks, which may be either circuit switched, such as the PLMN, PSTN (Public Switched Telephone Network) and ISDN (Integrated Services Digital Network), or packet switched networks, such as the Internet and the X.25. The packet switched portion of the core network CN1 comprises a Home Location Register HLR1, SGSN1 and GGSN1. The core network described herein is based on the third generation UMTS network. Core networks of other kinds of systems, such as the IS-41, may comprise other network elements.

In the third generation mobile networks, the packet switched portion utilizes the GPRS system. The GRPS system, which employs a 3G-radio access (such as the UMTS) or a 2G-radio access (such. as the GSM), comprises GPRS nodes, i.e. a Serving GPRS Node SGSN1 and a Gateway GPRS Node GGSN1. The primary functions of the SGSN include detecting GPRS-mobile stations MS within its service area, handling the registration processes of new mobile stations MS together with GPRS registers, sending data packets to and receiving them from the GPRS-mobile station MS and maintaining a register of the locations of the mobile stations MS within the service area. The operation of the SGSN according to the preferred embodiments of the invention is described below with reference to FIGS. 2 and 4.

The main functions of the GGSN comprise interaction with external data networks. The GGSN connects the GPRS network of the operator to external systems, such as the GPRS systems of other operators, data networks, such as the IP (Internet Protocol) network or the X.25 network, and to service switching centres. The GGSN comprises the PDP (Packet Data Protocol) addresses of GPRS mobile stations and their routing information, i.e. their SGSN addresses.

Within the area of one and the same network PLMN1, the serving network node SGSN1 and the gateway node GGSN1 are interconnected through an internal network of the operator, which may be implemented using the IP network, for example. The SGSN1 is connected to the GGSN2 preferably logically and/or physically, without using the GGSN1 in between.

Subscriber data are stored in GPRS subscriber registers HLR1 and HLR2 for MS1 and MS2, respectively, and they include the correspondence between the mobile station identifier, such as an MS-ISDN or an IMSI (International Mobile Subscriber Identity), and the PDP address. Both networks comprise a subscriber register storing the data of those subscribers whose home network the network in question is. The operation of a subscriber register according to the preferred embodiments of the invention will be described in connection with FIGS. 3 and 4.

A practical feature for use in network sharing is equivalent PLMN (Public Land Mobile Network). It facilitates the network selection (part of the cell selection process) made by the MS by giving equal priority to a PLMN that is equivalent to the home PLMN. Other features to guide the network selection process are available, for example the preferred PLMN list on the SIM (Subscriber Identity Module) or USIM (UMTS Subscriber Identity Module).

According to the present invention, information relating to predefined partner networks is maintained in the HLR and/or the SGSN and is used for selecting the appropriate GGSN. FIG. 1 depicts a first Mobile Station MS1 whose home network is the PLMN1, and a second Mobile Station MS2, which belongs to the PLMN2. The PLMN1 is a predefined partner network of the PLMN2, and they are typically in the same country. When MS2 is located within an area not covered by its home network PLMN2, it uses the PLMN1 to be connected. The MS1 is naturally using its home network PLMN1 to be connected. So both the MS1 and the MS2 are connected to the same SGSN1. The MS1 is connected through the SGSN1 to the GGSN1 and the MS2 is connected through the SGSN1 to the GGSN2. Therefore both the MS1 and the MS2 can access to their own PLMN IP services. If the home network of the MS is the PLMN2, it is connected to the GGSN of the home network, i.e. GGSN2, provided that the PLMN1 has agreed to connect PLMN2 mobile stations to their home network. The PLMN1 and the PLMN2 are partner networks for which the way to select the GGSN has been predefined (based on their agreement) within the information maintained in the subscriber register and/or the SGSN1. In addition to prior art means, a system or system network nodes that implement the functionality of the invention comprise means for processing information relating to the home network of the mobile station in a manner that will be described below. Existing network nodes and mobile stations comprise processors and memory that can be utilized in the operations of the invention. Any changes needed in implementing the invention may be carried out using supplements or updates of software routines and/or routines included in application specific integrated circuits (ASIC) and/or programmable circuits, such as EPLDs (Electrically Programmable Logic Device) or FPGAs (Field Programmable Gate Array).

FIG. 2 shows signalling according to the first preferred embodiment of the invention. According to the embodiment, a local APN Operator Identifier (APNOI) is configured in the SGSN1 for each predefined partner operator sharing the network. This embodiment therefore requires changes only to the SGSN.

In the GPRS network, the APN refers to the GGSN used by the GPRS core network. The APN sent by an MS comprises a mandatory APN network identifier and an optional APN operator identifier. The APN subscribed in the HLR comprises only the APN network identifier. The APN network identifier determines the IP network that the user wishes to connect to. The APN operator identifier defines the core network of the operator providing the access. In current systems the SGSN has one local APN operator identifier for the local (i.e. visited) network. When the SGSN searches the local network for a GGSN, it adds the APN operator identifier in question to the APN network identifier sent by the MS or configured in the HLR. If the use of the local network is not allowed, or if no suitable. local access is found, the SGSN searches the home network by adding the APN operator identifier of the home network (derived from IMSI) to the APN network identifier sent by the mobile station or configured in the HLR.

With reference to FIG. 2, the mobile station MS sends in step 2-1 an Activate PDP Context Request to the SGSN1, which checks the subscriber data it has received (during the attach procedure) from the HLR. In step 2-2, the SGSN1 decides whether the request can be accepted and whether it should use a GGSN in the visited network. According to the present invention, if the MS belongs to a predefined partner operator (typically having a GGSN in the same country), the SGSN1 wishes to establish a connection with the local GGSN of the partner operator. Therefore the SGSN1 checks the IMSI of the MS from the MNC/MCC (Mobile Network Code/Mobile Country Code) fields to know the MS home operator. The SGSN1 then checks a preconfigured list to find out if a local APN operator identifier is to be used for this MNC/MCC. Therefore, the information relating to predefined partner networks maintained in the SGSN1 comprises a preconfigured list of MNC/MCC codes and the related local APN operator identifiers. These APN operator identifiers identify the network of the partner operator.

If the MNC/MCC and its corresponding local APN operator identifier are configured in said list, the SGSN1 adds the corresponding local APN operator identifier to the APN network identifier. Next, a DNS query is carried out. The GPRS system employs a Domain Name Server (DNS) when a connection is to be set up to find out a GGSN address in the SGSN. The DNS returns the GGSN address of a GGSN located within a network belonging to the operator defined by the APN operator identifier. If said local APN operator identifier corresponds to the home operator of the MS, the mobile station MS is connected to the GGSN of its own operator, which is the GGSN1 in step 2-3, provided that the home network of the mobile station is the PLMN1. Correspondingly, the mobile station MS is connected to the GGSN of its own operator in step 2-4, i.e. to the GGSN2, provided that the PLMN2 is the home network of the mobile station.

If the MNC/MCC is not configured in said list, the mobile station MS does not belong to a predefined partner operator (e.g. the MS is roaming from another country), and the SGSN1 in step 2-2 either uses one local APN operator identifier as a default value (normal procedure used today as only one APNOI is defined by SGSN this one is the default) or selects a random APN operator identifier among the codes configured in the SGSN1. In this first (normal) case the visited GGSN, the GGSN1, is selected as the GGSN in step 2-3. The second case (random selection) is particularly suited if the SGSN belongs to a shared network not having its own GGSN. The random selection is then performed among the GGSNs of the operators owning the shared network.

It should be noted that the previous embodiment may be used in a variety of cases. For example, the local GGSN selected may be located in a neighbouring country and not in the same country. A typical case would be an operator who owns a network in two countries and, for practical reasons, prefers to concentrate its GGSNs in one country. With the above mechanism providing the proper configuration of local APN operator identifier in the partner operator SGSN, this can be easily carried out. So the term ‘local’ should be understood broadly as the APN operator identifier to be used when a VPLMN is to be selected. Another example could be two global operators having partnership agreements in many countries. When an MS of operator 1 moves into another country and uses the predefined partner network of operator 2, it may still be connected to a GGSN managed by operator 1 but located inside said another country. In other words, the home operator can be understood as having GGSNs in many countries. This can be achieved with the present invention by having in the preconfigured list many MNC/MCC codes (all belonging to one global operator) mapped to the same local APN operator identifier corresponding to the local network of this global operator.

FIG. 3 shows signalling according to a second preferred embodiment of the invention. According to the embodiment, SGSN addresses belonging to a mobile network PLMN2 that is a predefined partner network to the mobile network PLMN1 are configured in advance and information about them is maintained in the home location register HLR1. This embodiment therefore requires changes only to the HLR.

With reference to FIG. 3, the mobile station MS sends in step 3-1 an Attach Request or Routing Area Update Request to the SGSN 1, and the SGSN1 sends an Update Location Request to the HLR in step 3-2. Upon reception of the Update Location Request at the HLR, the routine checks in step 3-3 whether the SGSN1 belongs to a preconfigured list comprising SGSN addresses (or only address prefixes) of predefined partner operators. If it belongs to said list, the HLR sets a “VPLMN address allowed”-flag to a value indicating ‘No’, and if it does not, the value of the flag indicates ‘Yes’. This information is transmitted to the SGSN1 in step 3-4 with an Insert Subscriber Data message. When said flag is set to ‘Yes’ the MS sends a PDP Context Activation Request to the SGSN1 in step 3-6. Before that the SGSN1 informs in step 3-5 the MS that the Routing Area Update has been accepted. The GGSN is selected at the SGSN1 in step 3-7. When the “VPLMN address allowed”-flag has the value ‘No’ and the home network of the MS is the PLMN2, the GGSN selected at the SGSN1 is a GGSN located in the home network of the MS, i.e. GGSN2. The GGSN1 is the local GGSN of the PLMN1, and it is selected as the GGSN if the home network of the mobile station does not have an agreement with the PLMN1 and if the PLMN1 allows the use of the visited GGSN. When the home network of the mobile station is the PLMN1, the GGSN1 is selected as the GGSN, irrespective of the value of the “VPLMN address allowed”-flag.

According to a third preferred embodiment of the invention, a global operator operating in two or more countries, for example, may configure the HLR to maintain information about the SGSN addresses of its other networks, also referred to as “predefined partner networks belonging to the home network operator”. Upon reception of the Update Location Request at the HLR, the routine checks in step 3-3 whether the SGSN1 belongs to a preconfigured list containing SGSN addresses (or only address prefixes) of predefined partner operators. If it belongs to said list, the HLR sets a “VPLMN address allowed”-flag to a value indicating ‘Yes’, and if it does not, the value of the flag indicates ‘No’. When the “VPLMN address allowed”-flag has the value ‘Yes’, the GGSN selected at the SGSN1 is the GGSN1 of the current network, even if the mobile station were always to be connected to the home GGSN according to the default setting. This is typically suited for a case in which the same PLMN IP services can be accessed from the GGSN1 as from the home GGSN, as both belong to the same global operator.

According to a fourth preferred embodiment of the invention, an operator may configure the HLR to maintain information about the SGSN addresses and the APN operator identifier to be used by the MS when accessing the network from the SGSN in question.

With reference to FIG. 4, upon reception of the Update Location Request at the HLR, the routine checks in step 4-3 whether the SGSN1 belongs to a preconfigured list comprising SGSN addresses (or only address prefixes) of predefined partner operators. If it belongs to said list, the HLR sends the corresponding APN operator identifier to the SGSN1 within an Insert Subscriber Data message in step 44. This requires a new optional information element to be added to this message, and so new functionality is needed in both the SGSN and the HLR. Otherwise steps 4-1-4-6 in FIG. 4 correspond to steps 3-1-3-6 in FIG. 3 as described above in connection with the second embodiment. The SGSN should then use the APN operator identifier when querying the DNS in step 4-7. This is particularly suited for giving maximum flexibility to the home operator to control the GGSN selection from the HLR settings. For example, the home operator may identify an APN in a neighbouring country.

In the second, third and fourth embodiments, the information relating to the predefined partner networks is maintained in the HLR and it comprises a preconfigured list of SGSN addresses and their related “VPLMN address allowed”-flag values or APN operator identifiers.

The first, second and fourth preferred embodiments represent alternative ways of achieving the same goal in a specific situation where, based on an agreement between the operators involved, the home GGSN of a particular MS can be selected if it is located in same country as the SGSN. However, the solution presented in the first embodiment can be used in a variety of cases not covered by the second embodiment (e.g. the local GGSN selected is not located in the home country of the MS).

In the third embodiment of the invention the method according to the second embodiment is used for a different purpose. The third embodiment can be applied in a mobile communications system individually, or simultaneously with the first and/or the second embodiment.

As it can be seen, the invention relates to selecting, on the basis of information maintained in the system, the appropriate GGSN, which depends on the network in which the MS is located (indicated explicitly in the second, third and fourth embodiments by the SGSN address, and implicitly in the first embodiment by the SGSN to which the configuration according to the present invention is set) and on the home-PLMN of the MS (indicated explicitly in the first embodiment by the MNC/MCC derived from the IMSI, and implicitly in second, third and fourth embodiments by the HLR to which the configuration according to the present invention is set. So, the partner information preferably comprises indications showing directly or indirectly the location network of the MS and the home network of the MS.

The use of the equivalent PLMN functionality is not mandated by this invention. It is only a practical way to get the MS to select the network of a partner operator, but the proposed embodiments are not dependent on the method used to select the network.

The signalling messages and steps shown in FIGS. 2, 3 and 4 are simplified and aim only at describing the idea of the invention. Other signalling messages may be sent and/or other functions carried out between the messages and/or the steps. The signalling messages serve only as examples and they may contain only some of the information mentioned above. The messages may also include other information, and the titles of the messages may deviate from those given above.

Although the invention is presented with reference to specific embodiments, it is also conceivable to apply the invention in any situation involving a GGSN selection.

It is apparent to a person skilled in the art that as technology advances the basic idea of the invention can be implemented in various ways. The invention and its embodiments are therefore not restricted to the above examples, but they may vary within the scope of the claims. 

1. A method for selecting a gateway network node for a mobile station served by a serving network node, in a system where at least two network operators may share a radio network and the serving network node, the system comprising at least two gateway network nodes, the method comprising maintaining partner information about predefined partner networks, the partner information indicating that said network operators share the serving network node; and selecting a gateway network node for the mobile station on the basis of the partner information.
 2. A method according to claim 1, wherein the partner information comprises direct or indirect indications of the network in which the mobile station is located; and of the home network of the mobile station.
 3. A method according to claim 1, wherein the selection step of the method comprises the steps of checking on the basis of the partner information whether a mobile station is in the home network, in a predefined partner network of the home network, or in a network outside them; and selecting the gateway network node of the home network if the mobile station is in its home network; selecting the gateway network node of the home network if the mobile station is in a predefined partner network of the home network; or selecting the gateway network node of a visited network if the mobile station is outside its home network or predefined partner mobile networks of its home network.
 4. A method according to claim 1, wherein the selection step of the method comprises the steps of checking on the basis of the partner information whether the mobile station is in a network that is a predefined partner network of the one belonging to its home network operator; and selecting the gateway network node of a visited network if the mobile station is in a network that is a predefined partner network of the one belonging to its home network operator.
 5. A mobile communications system comprising at least one mobile station; a subscriber register for maintaining subscriber information of the mobile station; at least two networks to which the mobile station may connect when it is within the area of the network, one of the networks being the home network of the mobile station, the networks comprising at least one gateway network node for interaction between packet switched mobile networks and external data networks; and at least one serving network node for serving the mobile station while the mobile station is in the area of the serving network node, wherein the system is configured to maintain partner information about networks that are predefined partner networks of the home network, the home network sharing at least one serving gateway node with each of the predefined partner networks; and to select the gateway network node by utilizing the partner information.
 6. A system according to claim 5, wherein the partner information is maintained in the serving network node to indicate the networks sharing the serving network node.
 7. A system according to claim 6, wherein the serving network node is configured to compare the MNC/MCC code of the mobile station, in connection with the context activation of the mobile station, with APN operator identifiers stored for each network operator sharing the serving network node, said MNC/MCC code indicating explicitly the home network of the mobile station and said APN operator identifier indicating implicitly the partner information.
 8. A system according to claim 5, wherein the serving network node is also configured to connect a mobile station located in a mobile network that is a predefined partner network of its home network to the gateway network node of the home network.
 9. A system according to claim 5, wherein the partner information is maintained in a subscriber register.
 10. A system according to claim 9, wherein the subscriber register is configured to check the partner information in connection with the location update of the mobile station; set the value of a “Visitor-PLMN address allowed”-flag to ‘No’ if the mobile station is in a predefined partner network of the home network; and indicate the value of the flag to the serving network node.
 11. A system according to claim 5, wherein the serving network node is also configured to connect the mobile station located in a predefined partner network of its home network to the gateway network node of the home network.
 12. A system according to claim 5, wherein the subscriber register is configured to check the partner information in connection with the location update of the mobile station, the partner information comprising at least one network belonging to the home network operator; set value of the “Visitor-PLMN address allowed”-flag to ‘Yes’ if the mobile station is located in a network that is a predefined partner network of the one belonging to its home network operator; and indicate the value of the flag to the serving network node.
 13. A system according to claim 5, wherein the serving network node is also configured to connect the mobile station located in a predefined partner network of the one belonging to its home network operator to the gateway network node of the visited network on the basis of the partner information, the partner information comprising at least one network belonging to the home network operator.
 14. A system according to claim 9, wherein the subscriber register is configured to compare the MNC/MCC code of the mobile station with APN operator identifiers stored for each network operator sharing the network in connection with the location update of the mobile station; and indicate the result of the comparison to the serving network node.
 15. A subscriber register for maintaining subscriber information in a system comprising at least one mobile station, at least two networks to which the mobile station may connect when it is within the area of the network, one of the networks being the home network of the mobile station, the networks comprising at least one gateway network node for interaction between packet switched mobile networks and external data networks; and at least one serving network node for serving the mobile station while the mobile station is in the area of the serving network node, the subscriber register comprising a first routine for maintaining partner information about networks that are predefined partner networks of the network, the partner network and the home network sharing at least one serving gateway node; a second routine for checking the partner information of the mobile station; and a third routine for indicating, on the basis of the partner information, the gateway network node, to which the mobile station is to be connected, to the serving network node serving the mobile station.
 16. A serving network node for relaying packet switched data in a system comprising at least one mobile station; a subscriber register for maintaining subscriber information of the mobile station; and at least two networks to which the mobile station may connect when it is within the area of the network, one of the networks being the home network of the mobile station, the networks comprising at least one gateway network node for interaction between packet switched mobile networks and external data networks, the serving network node comprising a first routine for checking partner information about networks that are predefined partner networks of the network, the partner network and the home network sharing the serving gateway node; and a second routine for selecting a gateway network node on the basis of the partner information.
 17. A network node according to claim 16, wherein it further comprises a third routine for maintaining partner information.
 18. A network node according to claim 16, wherein it is the SGSN of a GPRS network. 